chore: dependency upgrades (pg, graphql, @types/pg, aws-sdk, etc.)#774
Merged
pyramation merged 3 commits intomainfrom Mar 4, 2026
Merged
chore: dependency upgrades (pg, graphql, @types/pg, aws-sdk, etc.)#774pyramation merged 3 commits intomainfrom
pyramation merged 3 commits intomainfrom
Conversation
…n type - Add graphql@16.13.0 to pnpm.overrides to force single version resolution (was resolving to both 16.12.0 and 16.13.0, causing duplicate @dataplan/pg instances with incompatible PgExecutor private types) - Fix pgsql-client connectPromise type: pg@8.19.0 changed Client.connect() return type from Promise<void> to Promise<Client>
…=> {})
Updated the type annotation to match @types/pg@8.18.0 where Client.connect()
now correctly returns Promise<Client> (was incorrectly typed as Promise<void>
in @types/pg@8.16.0). No behavioral change — the runtime always returned
Promise<Client>.
devin-ai-integration
bot
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Bulk dependency upgrades across the monorepo. Key version bumps:
pg@types/pggraphql@aws-sdk/client-s3/lib-storage@tanstack/react-queryreact/react-domoxfmt@babel/generator/typesinflektBuild fixes
"graphql": "16.13.0"topnpm.overrides: The lockfile was resolvinggraphqlto both16.12.0and16.13.0across workspace packages, creating two separate@dataplan/pginstances with incompatiblePgExecutorprivate types. This caused thegraphile-misc-pluginsbuild to fail withTS2345.connectPromisetype inpgsql-client:@types/pg@8.18.0correctedClient.connect()return type fromPromise<void>toPromise<Client>(matching what the runtime always returned). Updated the field type accordingly — no behavioral change, only the type annotation.Review & Testing Checklist for Human
pnpm.overridesgraphql pin is acceptable: It's pinned to"16.13.0"(exact), not a range. Future upgrades will need to update this override. Consider whether"^16.13.0"would be more appropriate (though it may re-introduce duplication).oxfmt0.26 → 0.36 compatibility: This is a large major version jump for a code formatting tool used ingraphql/codegen. Spot-check that codegen output is still correct.@aws-sdk3.971 → 3.1001 compatibility: Large version jump for S3 uploads. Confirm upload functionality still works.pgsql-clientconnection behavior: TheconnectPromisetype change is type-only, but worth a quick manual check that DB connections work as expected.graphql15.10.1 → 16.13.0 inintrospectronandcodegen-integration: These packages jumped a major version ofgraphql. Check for any schema introspection or codegen behavioral differences.Notes
examples/codegen-integrationpackage changedgraphqlfrom15.10.1to16.13.0— this is a major version jump worth extra scrutiny.Requested by: @pyramation
Link to Devin Session